Repository navigation
Document /flycommand:fly in the user guide and command reference - #35
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
Self-review rubric (scored adversarially against the diff and command output):
Summary: a documentation-only change, verified against the source and the existing tests, with CI green. No changes are requested. This review comment was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener). drafted by Claude on behalf of Daniel Stephenson |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
USER_GUIDE.mdandCOMMANDS.mdare updated to state that/flycommand:flyis handled the same as/fly, and that FlyCommand is still reached through it when/flyis also registered by another plugin (for example EssentialsX).CHANGELOG.mdunder## [Unreleased].Support for the namespaced form was shipped in 1.0.0 (#13) and is already covered by the README's tests and manual-validation sections, but it was not mentioned in the two guides read by server admins, and it is the form needed when a
/flyconflict exists.No tracking issue: the gap was found during a documentation accuracy sweep. The open-issue backlog was empty at triage, so no issues were deferred.
Sweep coverage
README.md,USER_GUIDE.md,COMMANDS.md,CONFIG.md,CHANGELOG.md,CONTRIBUTING.md,plugin.yml,pom.xml,.gitignore,minecraft-versions.jsonand the three workflows were checked againstMain.java, the tests and the remote tags (v1.0.0,dev). No other drift was found.Validation
Only docs are changed; code and manifest are left untouched. Each claim was checked against the source:
src/main/java/me/Daniel/FlyCommand/Main.java:22,command.getName().equalsIgnoreCase("fly")is matched, not the typed label, so every label that resolves to the command is handled.FlyCommandTest.otherLabelsForTheCommandAlsoToggleFlight, the handler is already run with the labelflycommand:fly, and flight is asserted to toggle.flycommandis derived fromname: FlyCommandinplugin.yml, lower-cased, as the standard Bukkit fallback prefix.The
Buildworkflow (Maven compile, tests and API-compat check) is run on this PR as usual, although no code or manifest is changed.This PR description was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).
🤖 Generated with Claude Code
drafted by Claude on behalf of Daniel Stephenson